Birmingham City Council
Tree preservation zone
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
THE BIRMINGHAM (349 - 359 BRISTOL ROAD, EDGBASTON) TPO 1990
- reference
- 563
- name
- THE BIRMINGHAM (349 - 359 BRISTOL ROAD, EDGBASTON) TPO 1990
- tree-preservation-order
- TPO 563
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.925826 52.448868,-1.925713 52.448611,-1.925552 52.448233,-1.925470 52.448049,-1.925405 52.447892,-1.925323 52.447869,-1.925117 52.447920,-1.924542 52.448057,-1.923974 52.448196,-1.923692 52.448261,-1.923910 52.448609,-1.924006 52.448757,-1.924101 52.448910,-1.924273 52.449180,-1.924560 52.449108,-1.924748 52.449067,-1.925129 52.448980,-1.925530 52.448910,-1.925744 52.448883,-1.925826 52.448868)))
- point
- POINT (-1.924794 52.448524)
- notes
- The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
- entry-date
- 2026-06-25
- start-date
- end-date
How to fix this issue
Your data is missing a tree-preservation-order.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Birmingham City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL